home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
001a
/
hunt100.zip
/
HUNT.DOC
< prev
Wrap
Text File
|
1991-11-15
|
18KB
|
489 lines
HUNT.ASP Hunt dialer for Procomm+
Introduction
Procomm+ 2.xx is a terrific comm program and I wouldn't trade it
for the world. Of course, no program is perfect for everyone,
and Procomm+ is no exception. One thing I always wanted was the
ability to dial multiple numbers from a single dialing directory
entry. Why? Just because I didn't like my dialing directory
cluttered up with 5 entries for the same BBS. So, thanks to
Datastorm's very powerful script langauge, HUNT was born. And
since scripts are now compiled, I thought I'd waste a few
microseconds and add a few other niceties.
Basically, HUNT is a script that works together with Procomm's
dialing directory. It will dial up to nine different numbers
from one entry and keep dialing until a modem answers. When a
modem answers, it will (optionally) open a log file and chain to
a user specified script.
NOTE!!!! HUNT is designed to work with a modem that uses the
Hayes AT command set. If yours does not, you will have to edit
HUNT.ASP to supply the equivalent commands and responses for your
modem. Most of the commands are taken from Procomm's
configuration or supplied in a configuration file. However, the
script expects the modem the to respond with "OK" to
configuration commands. It also expects verbal "CONNECT"
responses. If your modem fits this description, you should have
little problem.
November 15, 1991 page 1
HUNT.ASP Hunt dialer for Procomm+
INSTALLATION
Installation is simple, just copy HUNT.ASP to the disk or
directory where you keep the rest of your script files, either
the current DOS directory or the directory pointed to by the
set PCPLUS=~~~~ environment variable. HUNT should run as is
on MOST systems, but there are a few defaults you can change to
suit your system/preference. You will also need to set up a
configuration file for each dialing directory entry you will use
with HUNT.
To change HUNT's defaults, call up HUNT.ASP in your favorite
ASCII editor. Datastorm's PCEDIT, MS-DOS 5.0's EDIT, and (my
personal favorite) SemWare's Qedit, will all work fine. Near
the top of this file you will find the following variables:
string configdir = ""
integer cnorm = 31
integer cerr = 79
integer cwin = 30
integer RingWait = 5
The first four can only be changed by editing HUNT.ASP. The rest
can be changed through the configuration file and are discussed
in that section. For those variables, the values provided here
act as defaults.
CONFIGDIR
This should contain the directory where you will keep your .HNT
and/or .NOT configuratiion files. The default is blank, which
means the DOS directory you are logged into when you start
Procomm+. Note that HUNT does NOT look in the PCPLUS= directory
when searching for config files. As an example, I keep all my
config files in D:\COMM\DATA. As such, I have the following
line in HUNT.ASP:
configdir = "D:\DATA\COMM\"
The trailing "\" IS required. Also note that if you use
Procomm's Jot command from dialing directory, it will only look
in the current directory for the .NOT file. If in doubt, leave
it blank!
CNORM CERR CWIN
These are the colors used by HUNT.ASP. You may want to change
these if you have a monchrome monitor. Of course, you can also
change them to suit your taste. CNORM is used to display
informational messages, CWIN is the color of the dialing window,
and CERR is the color used for error messages. the defaults are:
CNORM bright white on blue
CERR bright white on red
CWIN yellow on blue
November 15, 1991 page 2
HUNT.ASP Hunt dialer for Procomm+
Using HUNT.ASP
To use HUNT, set it up as described in INSTALLATION. Then, for
each dialing directory entry you want to use HUNT with, do the
following:
1] Bring up the Procomm dialing directory. ALT-D
2] Use the cursor keys to highlight the entry to change
and press "r" to change the entry. You'll see a screen
like this:
/-| Revise Entry 8|---------------------\
| NAME: Flint Hills |
| NUMBER: pcboard <------------ script to run when connected
| BAUD: 38400 |
| PARITY: NONE |
| DATA BITS: 8 |
| STOP BITS: 1 |
| DUPLEX: FULL |
| PORT: DEFAULT |
| SCRIPT: HUNT <------------ required
| PROTOCOL: YMODEM-G |
| TERMINAL: ANSI |
| MODE: DIRECT <------------ required
| PASSWORD: |
| META FILE: |
| KBD FILE: |
| NOTE FILE: FHILLS <------------ required config file name
\---------------------------------------/
You will need to change the following:
NUMBER: HUNT will dial the numbers you specify in the
config file, so we use this entry to name the
script you want to run when a connection is
made. Generally, this will be whatever you
had under SCRIPT, before. This is optional and if
not used, it must be left blank
SCRIPT: This must be HUNT.
MODE: set to DIRECT. This will prevent Procomm from
trying to establish a connection before running
HUNT.
NOTE FILE: The name (without the . extension) of the file
the contains the configuration info for this entry.
HUNT will look first for a file having this name
and an extension of.HNT. If that cannot be found,
it will look for a file with this name and an
extension of .NOT (Procomm's default for a note
file).
November 15, 1991 page 3
HUNT.ASP Hunt dialer for Procomm+
The Configuration File(s)
This is where we keep the information the BBS you are calling.
In general, you should have one configuration file for each
dialing directory you use with HUNT.ASP. This file will contain
the phone numbers and the configuration paramaters for the BBS
you are calling. Configuration files must have the extension
of .HNT or .NOT, and MUST be located in the current directory,
or in the directory specified by the "configdir" variable
mentioned in the installation section.
If you use the .NOT extension and locate the file in the current
directory, you can use the Jot command from the dialing
directory to create/change the configuration file. This is the
recommended setup and HUNT has some features that make this setup
as painless as possible. Read on.
When HUNT starts up, it will perform the following steps to
locate a configuration file (using the above directory entry as
an example):
Prepend "configdir" value to "NOTE FILE:" value and append ".HNT"
and look for "FHILLS.HNT" (remember, by default "configdir" is
blank)
IF not found:
Prepend "configdir" value to "NOTE FILE:" value and append ".NOT"
and look for "FHILLS.NOT"
IF not found:
display error message and exit.
When HUNT finds the configuration file, it processes it and if
all goes well, begins the dialing sequence. If no phone numbers
were found in the configuration file, it will complain and exit.
HUNT displays each line of the file on your screen as it reads
them. This helpful in debugging configurations and can also be
used to display a reminder when calling. HUNT does NOT wait at
the end of screen, but instead clears the screen from line 3 and
continues.
November 15, 1991 page 4
HUNT.ASP Hunt dialer for Procomm+
The Configuration File(s)
Configuration File Format
Please refer to the sample configuration file (FHILLS.NOT) for
this section.
The very first line of the file must contain the string #HUNT
somewhere between column 1 and column 80. If HUNT does not find
this string, it will complain and exit. This is to prevent
HUNT from needlessly reading through a bogus file.
The remaining lines consist of a command in columns 1 thru 3; a
seperator in column 4 (any character may be used); and a command
argument in columns 5 thru 80. This is known as a positional
format. It isn't flexible, but it's quick and easy to implement
(hey come on, this IS a free program!!).
Any line that contains a "#" in column 1 is considered a comment
and is ignored. Lines containing invalid commands are also
ignored.
The folling commands are available:
Any commands that are not specified in this file will use the
default values listed below. Some of these are the defaults you
specify in Procomm's setup menus. These are denoted by "Defaults
to Procomm's value". Refer to your Procomm manual for more info.
NOTE: "string" denotes an alphanumeric argument
"##" denotes a numeric argument
"none" indicates that no argument is used
n1 string
n2 string
n3 string
n4 string
n5 string
n6 string
n7 string
n8 string
n9 string
These are the phone numbers to be dialed. They are dialed in
numeric sequence, n1, n2, etc. The format of the number
depaends on your modem. Most modems will ignore dashes and
underlines. Numbers are passed to your modem exactly as you
enter them here and may contain any special characters that
your modem recognizes. No default.
mi string
Modem initialization string. This is a command sent to your
modem when HUNT first starts up. By default, this is set to
whatever value you put in Procomm's modem setup screen. You
can overide that here, but it really shouldn't be necessary.
ms string
Modem setup string. This is a modem command sent after the
November 15, 1991 page 5
HUNT.ASP Hunt dialer for Procomm+
The Configuration File(s)
Configuration File Format
initialization string. This allows you to automatically
enable/disable special modem options on a per BBS basis. For
example, if you want to disable data compression on a Hayes
compatible MNP modem you could enter AT&K0 here. Essentially,
you can put any commands here to deviate from your noral modem
settings. No default.
cw ##
The number of seconds to wait for a response from your modem
after issuing the dial command. Defaults to Procomm's value.
rw ##
The number of rings to wait before trying the next number.
This is valid only if your modem returns a RING result code.
Default is 5.
log string
If desired, HUNT will automatically open a log file when it
makes a connection. "string" must be a valid DOS file name.
No default (no log file will be opened).
spd ##
Here's one that BBS sysop's will probably hate me for. This
tells HUNT to hangup if a connection is made at a speed less
than ##. For example, spd 9600 would cause HUNT to hangup
if a connection was made at say 2400 baud. HUNT would then
continue as if no connection was made. HUNT's speed detection
is a bit klutzy, it determines the connect speed based on the
modem's connect message, ie. CONNECT 1200, CONNECT 9600, etc.
If HUNT cannot determine the speed from the connect message,
it will assume the speed to be whatever you have in your
dialing directory entry.
Default 300.
end none
This tells HUNT to stop processing the configuration file.
When HUNT encounters this command, it will immediately close
the config file and continue on its merry way. Obviously,
this should be the very last command you use. This allows you
to use your config file to store notes or even use it as a log
file. In this way you can use your .NOT files as both a HUNT
config file and a note file. (I told you we made it as
painless as possible!)
November 15, 1991 page 6
HUNT.ASP Hunt dialer for Procomm+
Legal Tripe
DISCLAIMER: This software is distibuted as is. No warranties
are expressed or implied.
FEES: No fees are applicable to this program. It is distibuted
free of charge to anyone who wants to use it. You may freely
copy and distribute it provided you do so in it's orginal form
and charge no fee for the software itself.
CREDITS:
Procomm+ is a trademark of Datastorm Technologies, Inc.
MS-DOS is a trademark of Microsoft Corporation.
Qedit is a trademark of Applied Systems Technologies, Inc.
Please send questions, comments, bug reports to:
Larry McElderry
P.O.Box 1172
Manhattan, KS 66502
Compuserve ID: 74017,1630
Also available at EXEC-PC
November 15, 1991 page 7
HUNT.ASP Hunt dialer for Procomm+
HISTORY
version 1.00 initial release
Caveats: The dialing is somewhat clumsy. The design intent was
that pressing <spacebar> would cycle to the next
number, and pressing <ESC> would cancel the script.
It does work this way, but not always with the most
convenient timing. For version 2 I'm looking into
replacing a lot of the script with a "hook" program.
Since we tell Procomm that this is a direct
connection, it thinks a connection is made every time
you dial. As a result, an entry is made in the call
log file, and if this is one of multiple entries that
you marked for dialing, the sequence will stop here.
Also, the last call date and number of calls will be
updated at the time the entry is picked from the
directory. Call duration will also begin at that
point.
The ATE0 command to disable local echo from the modem
is hard coded and VERY important. Without it the rget
commands will respond to the modem's echo and the
script will fail miserably. As such, the script will
abort if the modem does not say "OK" when issued this
command. If the command to disable local echo is
something different for your modem, you will need to
change this.
Finally, the "spd" command should be used with
caution. Only the more popular baud rates are
supported (14400, 9600, 2400, 1200) and even these
require that the modem return the proper values in
it's connect message. Of course you can modify this
by changing the DOCONNECT proc. Also note that these
speeds refer to line speed, not necessarily DTE
speed. This too could be enhanced with a hook.
November 15, 1991 page 8